2.5.134 Maintenance Release Notes

Enhancements

  • Billing data has now been made available to the latest transactions in a policy. Previously, billing data was only available for the New Business and Renewal transactions in a given policy term as these are the "main" transactions, however, this made it difficult for users working in subsequent transactions to retrieve this data without having to navigate to those original transactions, specifically when configuring auto cancellations.

    Now, the following core billing fields are available for the latest transactions in a policy:

    • BillingPolicyTermCollectedAmount
    • BillingPolicyTermOutstandingAmount
    • BillingPolicyTermEarliestOverdueInvoiceDueDate
    • BillingPolicyTermOverdueAmount
    • BillingPolicyOutstandingAmount
    • BillingPolicyRemainingUnpaidAmount
    • BillingTotalTransactionPaymentAmount

  • Previously, only users with the System Administrator or Adjuster Supervisor security roles could use the Claims data source to pull data from a claim into a policy, where the policy had been attached. An enhancement has been implemented where data from claims associated with the policy can be viewed by any user.

    The ability to implement viewing claim data in policy is a custom feature, additional view/hide rights can be implemented by a user with the Product Designer role. A service account must be enabled to use this feature. Please contact your Insurity Account Representative for details.

  • The process responsible for retrieving policy documents in the Bridge Specialty Suite was not generating any results for Renewal Quote documents.

    When a policy is Auto Renewed, as per the current functionality, the system calculates a quote which should trigger the document generation and return the required documents. This would occur whenever a transaction would transition from Incomplete to Quoted for the first time. As a result, the procedure could not retrieve the documents associated to the transaction. A code change has been implemented to update the process to recognize policy transactions with the status as NULL.

  • When a Receipt Allocation is applied to a General Ledger - Suspense account, upon posting a batch receipt, users are now presented a warning message to inform them that a Receipt Allocation exists on a suspense account. This allows users who post cash receipts with an unknown Bill to Party to correctly re-allocate the receipt once the appropriate Bill to Party is known.
  • Previously, there were no General Ledger Account entries for offset transactions resulting from Cancel/Rewrite, Void, or OOSE transactions. The appropriate G/L accounts are now created whenever an offset transaction resulting from one of the above scenarios is triggered. For details on General Ledger entries for offset transactions, see the General Ledger Accounts section.

  • The billing fields added to the Billing Information panel in the OWPolicyCommon Standard Container in the previous release, 2.5.133, are now updated during the overnight job that runs when an ERP transaction is bound. The following fields are updated as part of this job:

    • Policy Term Overdue Amount
    • Policy Term Collected Amount
    • Policy Term Earliest Overdue Invoice Due Date
    • Policy Term Outstanding Amount
    • Policy Outstanding Amount
    • Policy Remaining Unpaid Amount

    For details on the billing fields above, see the OWPolicyCommon Standard Container section.

  • The Bridge Specialty Suite has been optimized in various areas to address issues of slowness related to the initializing system XML queries.

Bug Fixes

  • Previously, when a batch receipt was imported to the Bridge Specialty Suite for a policy that had multiple terms, the system did not allocate the On Account Balance (OAB) premium amount to the policy term. Instead, the system allocated the OAB to the Bill To Party. This occurred because the Web Service checked the Policy Number rather than the TermID. Since the policy number could be the same for different policy terms, the system could not allocate the charges to their respective terms. A new node for TermID has been added in the ImportBatchReceipt web service to check TermIDs when allocating OAB so that the imported policies will have their premium amount allocated to future charges accordingly. This bug has been fixed in versions 2.5.134 and 2.5.141.

  • While updating billing fields via web service calls, the expected fields were returning blank. The investigation revealed that the issue was caused by a referred Renewal transaction for which an Issue Quote job was triggered. In this scenario, the system creates a new Renewal transaction in Incomplete status. As a result, the Query Policy Header web service returns two instances for the same transaction, one for Renewal/Referred and another for Renewal/Incomplete.

    The billing code is unable to handle this scenario correctly, and as a result two records are inserted into the database table in billing when two jobs are executed simultaneously. The error then appears next time the job is executed.

    When the billing module needs to check if the data has already been exported into the policy module, an "unhandled exception" occurs. The issue has been resolved by adding code to retrieve current duplicates in the affected database table and then remove them. The data is then inserted again, but without duplicates. Additionally, a code change has been made to the ExportBillingInfoOperation.PostExportPolicyInfoJobs() web service to group the returned data before posting the job to the appropriate policy transactions, avoiding any duplicate entries.

  • When importing a new submission (New Business) via the PolicyWebService method, users were presented an error message "The User ID is not provided". The error would occur intermittently when the job attempted to generate documents and emails from the import. The issue would occur because the user session that executed the job would timeout and the system considered this user session as expired. The issue has been resolved by a code change to extend the user session when the web service is called and the system then validates when the session is expired in ICS.